args: allow to use multiple --refs arguments
#528
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Example: `git filter-repo --refs head1 --refs head2` Signed-off-by: Nikita Sliusarev <nsl@nebius.com>
nslsrv
force-pushed
the
args-multiple-refs
branch
from
b4f1924
to
92a83a1
Compare
|
@newren Hi, could you please review this one when you have some free time? This patch is good for cases when you need to rewrite ref history partially. |
|
Sorry for the delay. The PR is interesting, but it is going to break people that have already been passing multiple refs like so: or This would also invalidate part of the documentation, and would cause one of the tests in the regression testsuite to fail. This might make sense as an alternative way to have done things from the beginning, but I don't like breaking existing uses. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs arguments are passed to
git rev-listallowing user to configure the set of commits to operate on. IMHO it's important to be able to pass through any desirable rev-list configurations. This often requires using multiple--refsarguments.Examples:
git filter-repo --refs head1 --refs head2git filter-repo --refs='--glob:refs/heads/*' --refs='--glob:refs/tags/*'git filter-repo --refs='--glob:refs/heads/*' --refs='--not' --refs='master